docs: start on 23ai and step down only when a login is refused - #4
Open
haonguyen1915 wants to merge 1 commit into
Open
docs: start on 23ai and step down only when a login is refused#4haonguyen1915 wants to merge 1 commit into
haonguyen1915 wants to merge 1 commit into
Conversation
Testing against a real Oracle 11.2 server showed the client-version table does not decide whether a connection works - the 23ai client reached that server fine, and ORA-28040 only appeared once a side was configured to demand a newer logon protocol. Say plainly to start on 23ai and step down only when a login is actually refused, and mark the reach column as Oracle's support statement rather than a prediction of failure.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #3, from testing the guide's advice against a real server.
The page implied you pick a client to match your server's age. That is not what decides it. Connecting the 23ai client to an Oracle 11.2 server worked fine - including with an account left on a 10G-only password verifier - and
ORA-28040only appeared once a side was configured to demand logon version 12. The handshake is governed by the logon-protocol policy on each side and the account's stored verifier, none of which is visible from the version number.So the advice is now: start on 23ai, change only if a login is actually refused. The reach column is labelled as Oracle's support statement rather than a prediction of failure, and kept as the order to step down in. The ORA-28040/28041 section no longer opens by blaming the server's age.
Matching wording lands in the app itself (flex-table/flextable-app#625), so the option labels and the error message say the same thing.